Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ee5f9f966108735afb5d6eebb0124cc0acde7535f46b1790cc9260eba969d28

Tx prefix hash: 0e69650e6ee072c2f45112fb78ad423c187d91607cdfa069b3c09df4da51bc08
Tx public key: b5cb5849c4d8e7de1a18b9b3ee7ee25a4d4b9daf2f33bcb1fed5c08c6be8f585
Timestamp: 1728839012 Timestamp [UCT]: 2024-10-13 17:03:32 Age [y:d:h:m:s]: 00:165:16:31:11
Block: 1130835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118189 RingCT/type: yes/0
Extra: 01b5cb5849c4d8e7de1a18b9b3ee7ee25a4d4b9daf2f33bcb1fed5c08c6be8f58502110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae732deba8f8fa8d26d5325e1a7826b805837b91beb12db9f5d96f1a9172fba 0.600000000000 1613716 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": 1130845, "vin": [ { "gen": { "height": 1130835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae732deba8f8fa8d26d5325e1a7826b805837b91beb12db9f5d96f1a9172fba" } } ], "extra": [ 1, 181, 203, 88, 73, 196, 216, 231, 222, 26, 24, 185, 179, 238, 126, 226, 90, 77, 75, 157, 175, 47, 51, 188, 177, 254, 213, 192, 140, 107, 232, 245, 133, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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