Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05dbe2c5d02b93f50a561a59417c40091e9c0c7ad92c159f640a80bdecccb9af

Tx prefix hash: e21503bb622e5a04352b859e93c46081757569f67e7c62f093d8d99818ee2f64
Tx public key: 4af5d7bb7128269cfeb3b96408b90257ac9c88c2d005a255ccc8a8b5e62284ae
Timestamp: 1673323562 Timestamp [UCT]: 2023-01-10 04:06:02 Age [y:d:h:m:s]: 02:069:07:32:55
Block: 671442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571233 RingCT/type: yes/0
Extra: 014af5d7bb7128269cfeb3b96408b90257ac9c88c2d005a255ccc8a8b5e62284ae02110000000152542ceb000000000000000000

1 output(s) for total of 3.657917281000 dcy

stealth address amount amount idx
00: c7a8dfb8990ada485b77c2d9c041bee6298cf4ef652ef47edd19fcd1e17654c7 3.657917281000 1112909 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": 671452, "vin": [ { "gen": { "height": 671442 } } ], "vout": [ { "amount": 3657917281, "target": { "key": "c7a8dfb8990ada485b77c2d9c041bee6298cf4ef652ef47edd19fcd1e17654c7" } } ], "extra": [ 1, 74, 245, 215, 187, 113, 40, 38, 156, 254, 179, 185, 100, 8, 185, 2, 87, 172, 156, 136, 194, 208, 5, 162, 85, 204, 200, 168, 181, 230, 34, 132, 174, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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