Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db2b9ceb39f3478d58221512e8eac1195138140e81a503ab8eb88ccd5f401967

Tx prefix hash: 664177cc3a85d06a72f592b0a5c49e23ea43ba69f91e2694d16566b21e2e8627
Tx public key: 1a1a8dacd0fad2d9dcfff8c0d9b12bca6bb78cdfc9c1389f967b08c0b817b194
Timestamp: 1738433272 Timestamp [UCT]: 2025-02-01 18:07:52 Age [y:d:h:m:s]: 00:293:06:13:43
Block: 1209950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207355 RingCT/type: yes/0
Extra: 011a1a8dacd0fad2d9dcfff8c0d9b12bca6bb78cdfc9c1389f967b08c0b817b194021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c2f68f4720d2176bb31dc92a64a53d6bc0a268f7d033a5827d18c3fd39f6ae8 0.600000000000 1696697 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": 1209960, "vin": [ { "gen": { "height": 1209950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c2f68f4720d2176bb31dc92a64a53d6bc0a268f7d033a5827d18c3fd39f6ae8" } } ], "extra": [ 1, 26, 26, 141, 172, 208, 250, 210, 217, 220, 255, 248, 192, 217, 177, 43, 202, 107, 183, 140, 223, 201, 193, 56, 159, 150, 123, 8, 192, 184, 23, 177, 148, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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