Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae39f3a06164d478b5efbc4075f1addcb90d4fbfe834ba56bdd89fc3162742e

Tx prefix hash: 4ffade58684fa4dbb0ccc964f6e741debc422a6bacab47986075c743cc482b55
Tx public key: cc7dc25a79d365f1e68f17eecaf64605d7a3e7e8a11e6c0c5140c31fbd2ff199
Timestamp: 1716319779 Timestamp [UCT]: 2024-05-21 19:29:39 Age [y:d:h:m:s]: 01:093:07:18:07
Block: 1027046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325353 RingCT/type: yes/0
Extra: 01cc7dc25a79d365f1e68f17eecaf64605d7a3e7e8a11e6c0c5140c31fbd2ff1990211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f20a5d6fdb90fd7d50635f0318842347c152a012e3288c1ee0cfb633db158740 0.600000000000 1494465 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": 1027056, "vin": [ { "gen": { "height": 1027046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f20a5d6fdb90fd7d50635f0318842347c152a012e3288c1ee0cfb633db158740" } } ], "extra": [ 1, 204, 125, 194, 90, 121, 211, 101, 241, 230, 143, 23, 238, 202, 246, 70, 5, 215, 163, 231, 232, 161, 30, 108, 12, 81, 64, 195, 31, 189, 47, 241, 153, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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