Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b6469c80946eba62978135b6b61e18433314cf91c10461cea4a3a40e84ea8e

Tx prefix hash: 934a25a5658db0bf8f66d76079088a658549a71826d954c41568432d6b77b884
Tx public key: c79f3d6f03a1cd5ccb12b249b223b4a48a0252bdcdf2f640528d44be55c82db1
Timestamp: 1733432559 Timestamp [UCT]: 2024-12-05 21:02:39 Age [y:d:h:m:s]: 00:193:16:24:27
Block: 1168817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138158 RingCT/type: yes/0
Extra: 01c79f3d6f03a1cd5ccb12b249b223b4a48a0252bdcdf2f640528d44be55c82db1021100000010007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2c4314adb5ee71f69ff24365633e20b7101e1de17b792bd1b401c9a39e0189 0.600000000000 1654528 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": 1168827, "vin": [ { "gen": { "height": 1168817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2c4314adb5ee71f69ff24365633e20b7101e1de17b792bd1b401c9a39e0189" } } ], "extra": [ 1, 199, 159, 61, 111, 3, 161, 205, 92, 203, 18, 178, 73, 178, 35, 180, 164, 138, 2, 82, 189, 205, 242, 246, 64, 82, 141, 68, 190, 85, 200, 45, 177, 2, 17, 0, 0, 0, 16, 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