Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e51c85cc02d423a61a0acf55ff9549618e75266f91a63d32a982755452628ab8

Tx prefix hash: 180d2ef2131f87189c8b9469b06d335dee95e235ec05fd4f8000de8d74605254
Tx public key: 76d0f7ea0d2a9bb5d019b95cd1119e1741d272e5fbd6677665c56753f2935d67
Timestamp: 1682832231 Timestamp [UCT]: 2023-04-30 05:23:51 Age [y:d:h:m:s]: 02:192:19:48:58
Block: 749669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 657653 RingCT/type: yes/0
Extra: 0176d0f7ea0d2a9bb5d019b95cd1119e1741d272e5fbd6677665c56753f2935d670211000000027e406890000000000000000000

1 output(s) for total of 2.013889345000 dcy

stealth address amount amount idx
00: e746d2f112827461dd37c41d78c544e2e5db04596bd76e9dc45ff7867f17822a 2.013889345000 1197660 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 749679, "vin": [ { "gen": { "height": 749669 } } ], "vout": [ { "amount": 2013889345, "target": { "key": "e746d2f112827461dd37c41d78c544e2e5db04596bd76e9dc45ff7867f17822a" } } ], "extra": [ 1, 118, 208, 247, 234, 13, 42, 155, 181, 208, 25, 185, 92, 209, 17, 158, 23, 65, 210, 114, 229, 251, 214, 103, 118, 101, 197, 103, 83, 242, 147, 93, 103, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8