Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6f464045b3a2a1415596c64e4227e33a94b7a76d732469bf1348f4d47bd81d

Tx prefix hash: 684702d3fc7c1dc2a340ede9148801816df0b733697390d6415ba2e09282a320
Tx public key: b807ad902b8509364c562cef8d566c23192e511cfb93efb7445d4eb07f7cf87a
Timestamp: 1721149772 Timestamp [UCT]: 2024-07-16 17:09:32 Age [y:d:h:m:s]: 00:288:08:38:23
Block: 1067106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206004 RingCT/type: yes/0
Extra: 01b807ad902b8509364c562cef8d566c23192e511cfb93efb7445d4eb07f7cf87a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae97fee6e8f991b6c65a6c1fe1e34d9d5879d9885ff388002e670188f2ccb24a 0.600000000000 1537829 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": 1067116, "vin": [ { "gen": { "height": 1067106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae97fee6e8f991b6c65a6c1fe1e34d9d5879d9885ff388002e670188f2ccb24a" } } ], "extra": [ 1, 184, 7, 173, 144, 43, 133, 9, 54, 76, 86, 44, 239, 141, 86, 108, 35, 25, 46, 81, 28, 251, 147, 239, 183, 68, 93, 78, 176, 127, 124, 248, 122, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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