Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d80ce507d7f102084b43d2eb8268abda7f1237a6137b3fe182c876e366819b5e

Tx prefix hash: e480f2686751b6c08e1beb93a8e351da9cef36d3fbf0a9843a87647a10358805
Tx public key: 61eec5accc066d8357db58ff13f566e6883ae8a180eec71300ca41044e1e0b8a
Timestamp: 1732811390 Timestamp [UCT]: 2024-11-28 16:29:50 Age [y:d:h:m:s]: 00:116:06:30:04
Block: 1163672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82892 RingCT/type: yes/0
Extra: 0161eec5accc066d8357db58ff13f566e6883ae8a180eec71300ca41044e1e0b8a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7aafced5e4e5a6f6c88085fddd87803c481f898052aa7adf64f0e3f7576b0a 0.600000000000 1649339 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": 1163682, "vin": [ { "gen": { "height": 1163672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7aafced5e4e5a6f6c88085fddd87803c481f898052aa7adf64f0e3f7576b0a" } } ], "extra": [ 1, 97, 238, 197, 172, 204, 6, 109, 131, 87, 219, 88, 255, 19, 245, 102, 230, 136, 58, 232, 161, 128, 238, 199, 19, 0, 202, 65, 4, 78, 30, 11, 138, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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