Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f85dd13fe4cfb9e50d6d992d0a35db161b2799da7b048a611aaf721ed6083c9

Tx prefix hash: c941f0ece116349f49c677a8abec49fdfd5e7d44ee2245d88c8c60314ea90eae
Tx public key: aa8f705685e8d33e6e3d4dc10530e5bc2c1d1ec284cd41034f059a93cb9a399b
Timestamp: 1737614464 Timestamp [UCT]: 2025-01-23 06:41:04 Age [y:d:h:m:s]: 00:149:16:24:55
Block: 1203399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106656 RingCT/type: yes/0
Extra: 01aa8f705685e8d33e6e3d4dc10530e5bc2c1d1ec284cd41034f059a93cb9a399b02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b309ff01e04dd9ac5ef989cca79c464cf355bcd90fd69f459f9103f672d23544 0.600000000000 1690076 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": 1203409, "vin": [ { "gen": { "height": 1203399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b309ff01e04dd9ac5ef989cca79c464cf355bcd90fd69f459f9103f672d23544" } } ], "extra": [ 1, 170, 143, 112, 86, 133, 232, 211, 62, 110, 61, 77, 193, 5, 48, 229, 188, 44, 29, 30, 194, 132, 205, 65, 3, 79, 5, 154, 147, 203, 154, 57, 155, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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