Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a73a475254a9e07a3ca7bb497bb29834d142ea28dc6ee03703580341700673fb

Tx prefix hash: 7d9e761f126f8b6b633673c3455edf66adb9491192c43dd321a4711dde43870f
Tx public key: 6e45e23f91415d8f6e0eee996698b3c4e13c7b0d2b07642ed9eae9766bdb0963
Timestamp: 1744593262 Timestamp [UCT]: 2025-04-14 01:14:22 Age [y:d:h:m:s]: 00:219:23:15:01
Block: 1260962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154921 RingCT/type: yes/0
Extra: 016e45e23f91415d8f6e0eee996698b3c4e13c7b0d2b07642ed9eae9766bdb096302110000000a6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32362919c67eee86e1602bbe261df176a6fef925c6bd33b0facb85858ae806cd 0.600000000000 1748127 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": 1260972, "vin": [ { "gen": { "height": 1260962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32362919c67eee86e1602bbe261df176a6fef925c6bd33b0facb85858ae806cd" } } ], "extra": [ 1, 110, 69, 226, 63, 145, 65, 93, 143, 110, 14, 238, 153, 102, 152, 179, 196, 225, 60, 123, 13, 43, 7, 100, 46, 217, 234, 233, 118, 107, 219, 9, 99, 2, 17, 0, 0, 0, 10, 108, 152, 170, 61, 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