Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e4ed5520b8c316666628ad43b683f075efcc53b524c970d12e4c770b7970ecc

Tx prefix hash: 34db7ed203086df1e57d413a34564aa2c2499fd25a717545b9f486eeccc2c571
Tx public key: ff90ebd04a18092a184a13019dc3c46aa2cfe2d9e8c185f5508387d2d49b7ee2
Timestamp: 1728599741 Timestamp [UCT]: 2024-10-10 22:35:41 Age [y:d:h:m:s]: 01:055:23:42:03
Block: 1128854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298414 RingCT/type: yes/0
Extra: 01ff90ebd04a18092a184a13019dc3c46aa2cfe2d9e8c185f5508387d2d49b7ee202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09c6dbb465a2dc239f49d9142fcd876744378c83bd190fdfa35d63b6c4284edb 0.600000000000 1611677 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": 1128864, "vin": [ { "gen": { "height": 1128854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09c6dbb465a2dc239f49d9142fcd876744378c83bd190fdfa35d63b6c4284edb" } } ], "extra": [ 1, 255, 144, 235, 208, 74, 24, 9, 42, 24, 74, 19, 1, 157, 195, 196, 106, 162, 207, 226, 217, 232, 193, 133, 245, 80, 131, 135, 210, 212, 155, 126, 226, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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