Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3209ce8c3dcdb4d47f2f9c0c828f25f5d717c2d4af250a97556a2e5abdbd9f4f

Tx prefix hash: d08f075584bf1ef10adde030644f505d459d984d680436696b0271e951351aa2
Tx public key: 486da2c7d121afcffcbc546aa6b4540cf62e83f652c400ef2b4607a5ca9c2ce7
Timestamp: 1706810576 Timestamp [UCT]: 2024-02-01 18:02:56 Age [y:d:h:m:s]: 01:092:09:25:43
Block: 948193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327119 RingCT/type: yes/0
Extra: 01486da2c7d121afcffcbc546aa6b4540cf62e83f652c400ef2b4607a5ca9c2ce70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dc5f8638787d1bcbec2e34ed778c954e1c5cb298a14af43c961e638d77befdb 0.600000000000 1406565 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": 948203, "vin": [ { "gen": { "height": 948193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dc5f8638787d1bcbec2e34ed778c954e1c5cb298a14af43c961e638d77befdb" } } ], "extra": [ 1, 72, 109, 162, 199, 209, 33, 175, 207, 252, 188, 84, 106, 166, 180, 84, 12, 246, 46, 131, 246, 82, 196, 0, 239, 43, 70, 7, 165, 202, 156, 44, 231, 2, 17, 0, 0, 0, 1, 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