Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae606dd2bae18e68c9c021bbb75b0f88c08471dc9e97d30113cf7d732361ae4

Tx prefix hash: 89abf7a165a41179c04c03d2a97215fa9fbd18096d1a03fe68f962efbc319bcd
Tx public key: 836f99e6cbb266e7ae15c40a7595030f0b2486c2df4d6a6f96dc8cce72843533
Timestamp: 1710206476 Timestamp [UCT]: 2024-03-12 01:21:16 Age [y:d:h:m:s]: 01:089:20:25:27
Block: 976374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325250 RingCT/type: yes/0
Extra: 01836f99e6cbb266e7ae15c40a7595030f0b2486c2df4d6a6f96dc8cce728435330211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 481c780c5d4e48cf4696e9b73703b02ffaecfbe4e0b83254f845895a336f8d09 0.600000000000 1436367 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": 976384, "vin": [ { "gen": { "height": 976374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "481c780c5d4e48cf4696e9b73703b02ffaecfbe4e0b83254f845895a336f8d09" } } ], "extra": [ 1, 131, 111, 153, 230, 203, 178, 102, 231, 174, 21, 196, 10, 117, 149, 3, 15, 11, 36, 134, 194, 223, 77, 106, 111, 150, 220, 140, 206, 114, 132, 53, 51, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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