Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e39deb3cabaa3541660e7391bea202d9f210616c5a50e958c26621006a4e09

Tx prefix hash: 3c5cc1cec0bb9726754166cbf1ece78090af7315f08ea89db61c82bb6dfbfc44
Tx public key: a0cd43f0123e5fa8d6dbd6a2fdd17c64e12a56d32c508d4df66710b40a2c8084
Timestamp: 1703896913 Timestamp [UCT]: 2023-12-30 00:41:53 Age [y:d:h:m:s]: 01:017:02:22:36
Block: 924046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273559 RingCT/type: yes/0
Extra: 01a0cd43f0123e5fa8d6dbd6a2fdd17c64e12a56d32c508d4df66710b40a2c808402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56a61a852e8a5d60861db19fb4931ee51c8446fba6344180f70b30db7603f953 0.600000000000 1381788 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": 924056, "vin": [ { "gen": { "height": 924046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56a61a852e8a5d60861db19fb4931ee51c8446fba6344180f70b30db7603f953" } } ], "extra": [ 1, 160, 205, 67, 240, 18, 62, 95, 168, 214, 219, 214, 162, 253, 209, 124, 100, 225, 42, 86, 211, 44, 80, 141, 77, 246, 103, 16, 180, 10, 44, 128, 132, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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