Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0936d411f3ec2f62b1bd8951722267d4998fb5804cb19bdea8d0ca47db4af834

Tx prefix hash: 5cb025b2be2666149a98e0b5db1c1dd9ad733013179e72ab5e545120e311aa04
Tx public key: b34d3a51cfc4140eebc309a83183c3e169a05f173ad811df5104c89860dcb2b1
Timestamp: 1688231942 Timestamp [UCT]: 2023-07-01 17:19:02 Age [y:d:h:m:s]: 01:309:01:13:25
Block: 794440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482037 RingCT/type: yes/0
Extra: 01b34d3a51cfc4140eebc309a83183c3e169a05f173ad811df5104c89860dcb2b102110000000233af99f4000000000000000000

1 output(s) for total of 1.431168043000 dcy

stealth address amount amount idx
00: c0283e24776e841c662140ee64f1c1bfdfefd124114f14cb00c863ab73fc02bf 1.431168043000 1245193 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": 794450, "vin": [ { "gen": { "height": 794440 } } ], "vout": [ { "amount": 1431168043, "target": { "key": "c0283e24776e841c662140ee64f1c1bfdfefd124114f14cb00c863ab73fc02bf" } } ], "extra": [ 1, 179, 77, 58, 81, 207, 196, 20, 14, 235, 195, 9, 168, 49, 131, 195, 225, 105, 160, 95, 23, 58, 216, 17, 223, 81, 4, 200, 152, 96, 220, 178, 177, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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