Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6ce5443f0ab8b275e25a5d0218968fe10df6be4dd8383da9fd80298f51554d5

Tx prefix hash: 481552b9fd464e3e1c67da778027f6731a7438acf4398692e65b70b0d4541e5a
Tx public key: 451cb0981f0bf063091a49c822a61145859a7964a7613d154be67ec6a0e8fad9
Timestamp: 1749896079 Timestamp [UCT]: 2025-06-14 10:14:39 Age [y:d:h:m:s]: 00:160:03:03:47
Block: 1304779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112186 RingCT/type: yes/0
Extra: 01451cb0981f0bf063091a49c822a61145859a7964a7613d154be67ec6a0e8fad9021100000010bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1da653f26e3aa8c4342f23ec03a726af5a6d7b7f539661f4750eca64dd3b621 0.600000000000 1792372 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": 1304789, "vin": [ { "gen": { "height": 1304779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1da653f26e3aa8c4342f23ec03a726af5a6d7b7f539661f4750eca64dd3b621" } } ], "extra": [ 1, 69, 28, 176, 152, 31, 11, 240, 99, 9, 26, 73, 200, 34, 166, 17, 69, 133, 154, 121, 100, 167, 97, 61, 21, 75, 230, 126, 198, 160, 232, 250, 217, 2, 17, 0, 0, 0, 16, 191, 81, 178, 162, 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