Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67617b6d36a704a0c5160e6a427a1501fb07a10078f3abdd83d8bd9c408efa40

Tx prefix hash: 79517ffa1b5187da700d56e9858b15771dbc3ec3b5c997e8aa7925068caa5261
Tx public key: df6ae803b0fbb2ba344e1c1ca1506cd29ad531dbfab580106c53764c33e92f7e
Timestamp: 1685228410 Timestamp [UCT]: 2023-05-27 23:00:10 Age [y:d:h:m:s]: 02:165:08:51:11
Block: 769529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 637984 RingCT/type: yes/0
Extra: 01df6ae803b0fbb2ba344e1c1ca1506cd29ad531dbfab580106c53764c33e92f7e02110000000733af99f4000000000000000000

1 output(s) for total of 1.730737290000 dcy

stealth address amount amount idx
00: 4b2de5eddff8533adeeb09bb793bd9546e389f6af0ebb13ad9f7691df2de86a4 1.730737290000 1218778 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": 769539, "vin": [ { "gen": { "height": 769529 } } ], "vout": [ { "amount": 1730737290, "target": { "key": "4b2de5eddff8533adeeb09bb793bd9546e389f6af0ebb13ad9f7691df2de86a4" } } ], "extra": [ 1, 223, 106, 232, 3, 176, 251, 178, 186, 52, 78, 28, 28, 161, 80, 108, 210, 154, 213, 49, 219, 250, 181, 128, 16, 108, 83, 118, 76, 51, 233, 47, 126, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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