Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a97d2ed9dd12025132cf02c9dfd1f52a54c20bbe1764bcf3a832cef5e87cdd9

Tx prefix hash: 44ab8bf8d7c5dcfe8224f200e57bf9a35ac9c9236abbc960ce6182430faa70af
Tx public key: 6269e81c43275e1bad5c042c205d66d87820fec493c556c4e0c6c3a41839a8f1
Timestamp: 1736893301 Timestamp [UCT]: 2025-01-14 22:21:41 Age [y:d:h:m:s]: 00:155:05:15:24
Block: 1197462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110617 RingCT/type: yes/0
Extra: 016269e81c43275e1bad5c042c205d66d87820fec493c556c4e0c6c3a41839a8f1021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef19e6194faa81d4e37f6bc12d71d47a294acf81d15cf64352845764e18605b2 0.600000000000 1684069 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": 1197472, "vin": [ { "gen": { "height": 1197462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef19e6194faa81d4e37f6bc12d71d47a294acf81d15cf64352845764e18605b2" } } ], "extra": [ 1, 98, 105, 232, 28, 67, 39, 94, 27, 173, 92, 4, 44, 32, 93, 102, 216, 120, 32, 254, 196, 147, 197, 86, 196, 224, 198, 195, 164, 24, 57, 168, 241, 2, 17, 0, 0, 0, 3, 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