Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89c3f20aa4eddd97f06e99ade6b6e21df350bb650a8480dc73274280da1cccd

Tx prefix hash: 2ae6426102f3e846e3aef5ecf98d45c560ff623a143c4361c3508c75920cb34d
Tx public key: 8da882fad1730c6fb7f41c9b1bca5063942fdb3fbdabc3e3fa45fcc0ec830875
Timestamp: 1755403956 Timestamp [UCT]: 2025-08-17 04:12:36 Age [y:d:h:m:s]: 00:049:20:52:53
Block: 1348259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35407 RingCT/type: yes/0
Extra: 018da882fad1730c6fb7f41c9b1bca5063942fdb3fbdabc3e3fa45fcc0ec83087502110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11b3707d8ebe4c0ad6439447b4ba0ba1863f240f4429dc6fc3494027f69b6673 0.600000000000 1836184 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": 1348269, "vin": [ { "gen": { "height": 1348259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11b3707d8ebe4c0ad6439447b4ba0ba1863f240f4429dc6fc3494027f69b6673" } } ], "extra": [ 1, 141, 168, 130, 250, 209, 115, 12, 111, 183, 244, 28, 155, 27, 202, 80, 99, 148, 47, 219, 63, 189, 171, 195, 227, 250, 69, 252, 192, 236, 131, 8, 117, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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