Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df53607a84bb48adb012cf3e4d0e5f21dcfcd940b008e53043bc83b27008f18f

Tx prefix hash: dc865637dc19ffb2425d9a25cf9e4de987e20f1723694b47139e803f65636907
Tx public key: 979c7dac669898939dbf2560a55d7edd2de324fdd40d43231ebe3d896b4a580c
Timestamp: 1734945280 Timestamp [UCT]: 2024-12-23 09:14:40 Age [y:d:h:m:s]: 00:176:12:08:14
Block: 1181373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125832 RingCT/type: yes/0
Extra: 01979c7dac669898939dbf2560a55d7edd2de324fdd40d43231ebe3d896b4a580c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b60eac5ec64df8dc07ea039bf5314897f207caaad9b5e9f7e5ec748102d2932f 0.600000000000 1667792 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": 1181383, "vin": [ { "gen": { "height": 1181373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b60eac5ec64df8dc07ea039bf5314897f207caaad9b5e9f7e5ec748102d2932f" } } ], "extra": [ 1, 151, 156, 125, 172, 102, 152, 152, 147, 157, 191, 37, 96, 165, 93, 126, 221, 45, 227, 36, 253, 212, 13, 67, 35, 30, 190, 61, 137, 107, 74, 88, 12, 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