Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e8680b38118f8727fe872b444f58e21da39d6eaf2060769b6b9512406ada0e

Tx prefix hash: ed6b34cc7f84a2697f8fd9e8663cfff75fa7f233534230795acd8c41b7c78eb2
Tx public key: afd534df25ace6ecfcb78be9952d62bda3ba7c8a682e4cee37dd3aa33a867bff
Timestamp: 1712878447 Timestamp [UCT]: 2024-04-11 23:34:07 Age [y:d:h:m:s]: 00:359:14:08:15
Block: 998496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257084 RingCT/type: yes/0
Extra: 01afd534df25ace6ecfcb78be9952d62bda3ba7c8a682e4cee37dd3aa33a867bff02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd567fcb2eaaf823067bc4cc8d11f654d46b16d6172dc4adf749ce47315f65d8 0.600000000000 1458948 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": 998506, "vin": [ { "gen": { "height": 998496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd567fcb2eaaf823067bc4cc8d11f654d46b16d6172dc4adf749ce47315f65d8" } } ], "extra": [ 1, 175, 213, 52, 223, 37, 172, 230, 236, 252, 183, 139, 233, 149, 45, 98, 189, 163, 186, 124, 138, 104, 46, 76, 238, 55, 221, 58, 163, 58, 134, 123, 255, 2, 17, 0, 0, 0, 14, 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