Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c96028a809e9739c66673f3077c577c7b5d1dd179bf7a28ba4fc3e7024b9ac4

Tx prefix hash: 2f071f55bbfa942a8077525a504ddf16d1dba305f6a3f4de83ba356f8608ae40
Tx public key: 43142958d8102dd718ad91c05a576d60dc74ec90f88ddd4ec94b2b3352c4cd9b
Timestamp: 1748891491 Timestamp [UCT]: 2025-06-02 19:11:31 Age [y:d:h:m:s]: 00:164:14:07:25
Block: 1296532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115319 RingCT/type: yes/0
Extra: 0143142958d8102dd718ad91c05a576d60dc74ec90f88ddd4ec94b2b3352c4cd9b02110000000cbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b70f9538fac9f6fb3c9a825f17bd47fbf91204d39fe340f2daa0334442aaa10 0.600000000000 1784043 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": 1296542, "vin": [ { "gen": { "height": 1296532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b70f9538fac9f6fb3c9a825f17bd47fbf91204d39fe340f2daa0334442aaa10" } } ], "extra": [ 1, 67, 20, 41, 88, 216, 16, 45, 215, 24, 173, 145, 192, 90, 87, 109, 96, 220, 116, 236, 144, 248, 141, 221, 78, 201, 75, 43, 51, 82, 196, 205, 155, 2, 17, 0, 0, 0, 12, 191, 81, 178, 162, 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