Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c2ee40fb150cfcdd78abede89c1ccad6d53dee5caee40b39bd5704c5e96ddc

Tx prefix hash: a98e5dbf109fa5e7c5ecc717a146867fcdecea1a3e7a1763804af1d723a2679f
Tx public key: b183b962a11b3a028ab012b6d13602ce4b9f8da69e93f1cf80034e49c18a2845
Timestamp: 1726095708 Timestamp [UCT]: 2024-09-11 23:01:48 Age [y:d:h:m:s]: 00:214:12:04:15
Block: 1108106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153135 RingCT/type: yes/0
Extra: 01b183b962a11b3a028ab012b6d13602ce4b9f8da69e93f1cf80034e49c18a284502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f695929659a26f797fc069165b8b19203b554c8f7e7bf341466c0095fa766f86 0.600000000000 1585881 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": 1108116, "vin": [ { "gen": { "height": 1108106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f695929659a26f797fc069165b8b19203b554c8f7e7bf341466c0095fa766f86" } } ], "extra": [ 1, 177, 131, 185, 98, 161, 27, 58, 2, 138, 176, 18, 182, 209, 54, 2, 206, 75, 159, 141, 166, 158, 147, 241, 207, 128, 3, 78, 73, 193, 138, 40, 69, 2, 17, 0, 0, 0, 5, 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