Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b99c710986f89918f97b2e94cc338c2f546a96190400ba21fd1be8da4ddc34

Tx prefix hash: 698af3e4d1a6c99d5222740eaaaa97523f79ebc590bc2af3021fae48d8b88a9e
Tx public key: 8ff4f3274d2557705f242a0b86fdc08d43501e3f8a934bb567a59d98fd104e8e
Timestamp: 1727383631 Timestamp [UCT]: 2024-09-26 20:47:11 Age [y:d:h:m:s]: 00:180:07:16:00
Block: 1118768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128657 RingCT/type: yes/0
Extra: 018ff4f3274d2557705f242a0b86fdc08d43501e3f8a934bb567a59d98fd104e8e02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a19565079d3c1994bef77a23e3f38844e3d4476a600c5578105e4ce550bf4d8 0.600000000000 1600075 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": 1118778, "vin": [ { "gen": { "height": 1118768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a19565079d3c1994bef77a23e3f38844e3d4476a600c5578105e4ce550bf4d8" } } ], "extra": [ 1, 143, 244, 243, 39, 77, 37, 87, 112, 95, 36, 42, 11, 134, 253, 192, 141, 67, 80, 30, 63, 138, 147, 75, 181, 103, 165, 157, 152, 253, 16, 78, 142, 2, 17, 0, 0, 0, 10, 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