Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd494fdfc6fd38ca8ee44d93383e8017f370e480ad21724e2eed00580ec67257

Tx prefix hash: 0c77d5991dfcc5b8a6ac4b3c736a751f9e1a1a4788ace91ba35a0aa042b58fb0
Tx public key: f516db9edeb6614f98acebcb620738eec50f36dad8c6339ef41e9e5e693fa88f
Timestamp: 1718330377 Timestamp [UCT]: 2024-06-14 01:59:37 Age [y:d:h:m:s]: 00:222:13:51:45
Block: 1043723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159224 RingCT/type: yes/0
Extra: 01f516db9edeb6614f98acebcb620738eec50f36dad8c6339ef41e9e5e693fa88f0211000000048fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97703f8a16bb1e55db59fcc644845210a0d89b0b6c3710d9f58de3719a35da6e 0.600000000000 1512882 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": 1043733, "vin": [ { "gen": { "height": 1043723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97703f8a16bb1e55db59fcc644845210a0d89b0b6c3710d9f58de3719a35da6e" } } ], "extra": [ 1, 245, 22, 219, 158, 222, 182, 97, 79, 152, 172, 235, 203, 98, 7, 56, 238, 197, 15, 54, 218, 216, 198, 51, 158, 244, 30, 158, 94, 105, 63, 168, 143, 2, 17, 0, 0, 0, 4, 143, 218, 155, 45, 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