Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81448df2d658c8a9faa27aa9f836a3945ebc9a229ed90dcf2f43a911e83b43e8

Tx prefix hash: 6e91c9ea523708e974fbb4e32177cafd0eb1cc774a6ad11529804120da20e012
Tx public key: b0038da3e640fc34af92206b8ff2c1cf89e883fe3bbc8fdaf4ea75003a5c7ace
Timestamp: 1701460269 Timestamp [UCT]: 2023-12-01 19:51:09 Age [y:d:h:m:s]: 01:161:09:25:17
Block: 903840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376534 RingCT/type: yes/0
Extra: 01b0038da3e640fc34af92206b8ff2c1cf89e883fe3bbc8fdaf4ea75003a5c7ace02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.621159106000 dcy

stealth address amount amount idx
00: c1ac7b9c3a9ea171ed2fa5b744a1c0b6aaf90af0a168a1dfddf2c8a2b805a976 0.621159106000 1360533 of 0

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": 903850, "vin": [ { "gen": { "height": 903840 } } ], "vout": [ { "amount": 621159106, "target": { "key": "c1ac7b9c3a9ea171ed2fa5b744a1c0b6aaf90af0a168a1dfddf2c8a2b805a976" } } ], "extra": [ 1, 176, 3, 141, 163, 230, 64, 252, 52, 175, 146, 32, 107, 143, 242, 193, 207, 137, 232, 131, 254, 59, 188, 143, 218, 244, 234, 117, 0, 58, 92, 122, 206, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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