Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af5e5633098be627ab0d3aa11d1955dec9e60ac8ebadca9d41d1d34acc508fb

Tx prefix hash: 400183dd6eac39cab600385b25b86e55fbad0b8acc2bece65a5ec6d6168302c9
Tx public key: f40a3bcb023c98b2cb09c42ab8ede5274039cdac01ca31d6bf853d70d4df4030
Timestamp: 1707367246 Timestamp [UCT]: 2024-02-08 04:40:46 Age [y:d:h:m:s]: 01:134:22:14:10
Block: 952813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357343 RingCT/type: yes/0
Extra: 01f40a3bcb023c98b2cb09c42ab8ede5274039cdac01ca31d6bf853d70d4df4030021100000002ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61c48e004b930ed104c7dfd2a03ed8f9180b57b095abd1ce752d677dcf9c03ff 0.600000000000 1411945 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": 952823, "vin": [ { "gen": { "height": 952813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61c48e004b930ed104c7dfd2a03ed8f9180b57b095abd1ce752d677dcf9c03ff" } } ], "extra": [ 1, 244, 10, 59, 203, 2, 60, 152, 178, 203, 9, 196, 42, 184, 237, 229, 39, 64, 57, 205, 172, 1, 202, 49, 214, 191, 133, 61, 112, 212, 223, 64, 48, 2, 17, 0, 0, 0, 2, 236, 87, 178, 52, 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