Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394231af5cdedfa8d328ff28f2b30bd3f54ad671b9fb3d7f60ffe41a29ec3eec

Tx prefix hash: 3e966e72890f1e1b1d2c6af134dae8f4ee3f5f69622e196b07a84a39da43ff8d
Tx public key: 0293e1da1f28e9fec507b0cfa08b0c248f7635bdeb4906339747dc5c7828a929
Timestamp: 1712178120 Timestamp [UCT]: 2024-04-03 21:02:00 Age [y:d:h:m:s]: 01:006:07:19:39
Block: 992676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265500 RingCT/type: yes/0
Extra: 010293e1da1f28e9fec507b0cfa08b0c248f7635bdeb4906339747dc5c7828a92902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1de6322fa270cdf34f9d552e377b4b014d614c826636c43aa5b52eec3ebe625b 0.600000000000 1453050 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": 992686, "vin": [ { "gen": { "height": 992676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1de6322fa270cdf34f9d552e377b4b014d614c826636c43aa5b52eec3ebe625b" } } ], "extra": [ 1, 2, 147, 225, 218, 31, 40, 233, 254, 197, 7, 176, 207, 160, 139, 12, 36, 143, 118, 53, 189, 235, 73, 6, 51, 151, 71, 220, 92, 120, 40, 169, 41, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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