Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f53b669ac9902b5a05c268e720c37e7f7882576fabd769167cff298ecef4c15

Tx prefix hash: 61f12f4992dfef15c2cb764817a6a56627594326c3f515f3bb378cd1cff6959d
Tx public key: d0152e8c647ec00fe12d4cb184226f81d3d19303f3e275c9ca871334fe763ff8
Timestamp: 1695995076 Timestamp [UCT]: 2023-09-29 13:44:36 Age [y:d:h:m:s]: 01:258:20:40:45
Block: 858740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446040 RingCT/type: yes/0
Extra: 01d0152e8c647ec00fe12d4cb184226f81d3d19303f3e275c9ca871334fe763ff8021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.876270001000 dcy

stealth address amount amount idx
00: 4c739caad3e050c191f4b52379efc98103badc13e23ebf346b1fca00cd03a033 0.876270001000 1312930 of 0

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": 858750, "vin": [ { "gen": { "height": 858740 } } ], "vout": [ { "amount": 876270001, "target": { "key": "4c739caad3e050c191f4b52379efc98103badc13e23ebf346b1fca00cd03a033" } } ], "extra": [ 1, 208, 21, 46, 140, 100, 126, 192, 15, 225, 45, 76, 177, 132, 34, 111, 129, 211, 209, 147, 3, 243, 226, 117, 201, 202, 135, 19, 52, 254, 118, 63, 248, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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