Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a197d9cf5f7b0e5d8d0252b0ea4f61bfcaed56254b5a88b23b276dac7bdde0

Tx prefix hash: d26dfd4b126924c4646b8383f1383e569dfd28a787d43085c602bcb2a3b70ad3
Tx public key: 4d5457f0abc32d35e2a603e9bb13aa147f91f62cf97345f16d13c134ba1e03b6
Timestamp: 1720718999 Timestamp [UCT]: 2024-07-11 17:29:59 Age [y:d:h:m:s]: 00:195:08:59:58
Block: 1063524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139742 RingCT/type: yes/0
Extra: 014d5457f0abc32d35e2a603e9bb13aa147f91f62cf97345f16d13c134ba1e03b602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6a493d02fd57aa52cdf23b48c52a53af172635545583b06ae5c9f7594eb74b 0.600000000000 1534039 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": 1063534, "vin": [ { "gen": { "height": 1063524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6a493d02fd57aa52cdf23b48c52a53af172635545583b06ae5c9f7594eb74b" } } ], "extra": [ 1, 77, 84, 87, 240, 171, 195, 45, 53, 226, 166, 3, 233, 187, 19, 170, 20, 127, 145, 246, 44, 249, 115, 69, 241, 109, 19, 193, 52, 186, 30, 3, 182, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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