Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e102dd76d1dd1bee38dce3a34995164309d7467dc0d981f0399e1f6caec6d8

Tx prefix hash: 610b583e0e0a0f4c31d89c35d859c5fcdccd29594c6f276a4daf884d8a588c16
Tx public key: 884372b213363183b13be02d1b5a7796966b54a15a6c5cd97c70ce932883fcc2
Timestamp: 1731221057 Timestamp [UCT]: 2024-11-10 06:44:17 Age [y:d:h:m:s]: 00:014:04:04:40
Block: 1150495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10142 RingCT/type: yes/0
Extra: 01884372b213363183b13be02d1b5a7796966b54a15a6c5cd97c70ce932883fcc2021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a6ed50dd30d175cc3a13b60342db2790b7e5482e1e63c4ee804d9c203141ef 0.600000000000 1635828 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": 1150505, "vin": [ { "gen": { "height": 1150495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a6ed50dd30d175cc3a13b60342db2790b7e5482e1e63c4ee804d9c203141ef" } } ], "extra": [ 1, 136, 67, 114, 178, 19, 54, 49, 131, 177, 59, 224, 45, 27, 90, 119, 150, 150, 107, 84, 161, 90, 108, 92, 217, 124, 112, 206, 147, 40, 131, 252, 194, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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