Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6904ef33a54bdf82a15a1d0db39c285232cdbc6903a3b144c91a21a21ed743d

Tx prefix hash: 14d9092abf5a9bee8fb918d4593bdbe73d71e08558703c700fa870b51a6c1f3f
Tx public key: ae0ce2a73c97fa750dc256c75f4cac857398fd4ee8940fc740a34a9b21cf9f7c
Timestamp: 1721162889 Timestamp [UCT]: 2024-07-16 20:48:09 Age [y:d:h:m:s]: 00:262:02:46:20
Block: 1067210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187239 RingCT/type: yes/0
Extra: 01ae0ce2a73c97fa750dc256c75f4cac857398fd4ee8940fc740a34a9b21cf9f7c02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76e1fcda75b3b94603cf503ff044ce64c4d0c7f18554294b5c446134324dfc48 0.600000000000 1537959 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": 1067220, "vin": [ { "gen": { "height": 1067210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76e1fcda75b3b94603cf503ff044ce64c4d0c7f18554294b5c446134324dfc48" } } ], "extra": [ 1, 174, 12, 226, 167, 60, 151, 250, 117, 13, 194, 86, 199, 95, 76, 172, 133, 115, 152, 253, 78, 232, 148, 15, 199, 64, 163, 74, 155, 33, 207, 159, 124, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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