Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ca57c1bf204c2a21cc9b8179dc911d2e243bdfd4c35ec64712ab47d3bf8c562

Tx prefix hash: 3ff7287748cdb9496f95b1d54d79aa9ef2da7865ee562dae291784bf42c97b4f
Tx public key: 5798a3e5334f3b91cc3d875444b5d40159dbb0c31c3345286df22ffc9c0834f9
Timestamp: 1704000428 Timestamp [UCT]: 2023-12-31 05:27:08 Age [y:d:h:m:s]: 02:004:02:10:11
Block: 924904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522699 RingCT/type: yes/0
Extra: 015798a3e5334f3b91cc3d875444b5d40159dbb0c31c3345286df22ffc9c0834f9021100000003ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a350137e56809afd55c51a4d63252bb6fd478a58edac5b4ae3dd178c441ced45 0.600000000000 1382664 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": 924914, "vin": [ { "gen": { "height": 924904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a350137e56809afd55c51a4d63252bb6fd478a58edac5b4ae3dd178c441ced45" } } ], "extra": [ 1, 87, 152, 163, 229, 51, 79, 59, 145, 204, 61, 135, 84, 68, 181, 212, 1, 89, 219, 176, 195, 28, 51, 69, 40, 109, 242, 47, 252, 156, 8, 52, 249, 2, 17, 0, 0, 0, 3, 172, 50, 141, 17, 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