Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae5ba4c20ae2587d5692d4addc94ec60a1862303bc9f724015c0afc88f879e54

Tx prefix hash: 601be4d9f4c40157193854127e22b1ad0c2767139da72468c9dcdaeffa9b2b46
Tx public key: 9e58f42290251e22acf98e7ece471cf9a442dfd10de6f180ff703dc2a407b2e3
Timestamp: 1707415404 Timestamp [UCT]: 2024-02-08 18:03:24 Age [y:d:h:m:s]: 01:301:04:25:06
Block: 953214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474058 RingCT/type: yes/0
Extra: 019e58f42290251e22acf98e7ece471cf9a442dfd10de6f180ff703dc2a407b2e302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b95418b869ab4bb6a48eb404d0dc177cc27652f74628dd8b19e3629257453d07 0.600000000000 1412398 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": 953224, "vin": [ { "gen": { "height": 953214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b95418b869ab4bb6a48eb404d0dc177cc27652f74628dd8b19e3629257453d07" } } ], "extra": [ 1, 158, 88, 244, 34, 144, 37, 30, 34, 172, 249, 142, 126, 206, 71, 28, 249, 164, 66, 223, 209, 13, 230, 241, 128, 255, 112, 61, 194, 164, 7, 178, 227, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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