Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc0b73ae21ae371f3dcd0cd10b2ac0efa8bae9ef0b1573582ac913d72edab6ed

Tx prefix hash: 898e73007d903f9978ee31a54cf0ba9d084f790dcf1f6d1d7e6769abc1d8c8b9
Tx public key: ed6cfd72a3e18815499839ebb6ab8023d27ada8fbbfff0a07537c0214d25b9a8
Timestamp: 1709646755 Timestamp [UCT]: 2024-03-05 13:52:35 Age [y:d:h:m:s]: 01:069:00:08:48
Block: 971730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310333 RingCT/type: yes/0
Extra: 01ed6cfd72a3e18815499839ebb6ab8023d27ada8fbbfff0a07537c0214d25b9a80211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f16a3b42527fa112c1cbbea64170e333ab79a75398d8b51b9cd751b95160a9ec 0.600000000000 1431631 of 15

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": 971740, "vin": [ { "gen": { "height": 971730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f16a3b42527fa112c1cbbea64170e333ab79a75398d8b51b9cd751b95160a9ec" } } ], "extra": [ 1, 237, 108, 253, 114, 163, 225, 136, 21, 73, 152, 57, 235, 182, 171, 128, 35, 210, 122, 218, 143, 187, 255, 240, 160, 117, 55, 192, 33, 77, 37, 185, 168, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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