Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f0f1f642437b94e51ed28f7b73e138fd357572fda1cfb79e7995b9de8c2a39e

Tx prefix hash: 8341af0caaa6f22775a6c5dabd90c17c54c41246e908972f1cf6f3cb337b7039
Tx public key: 0e0d1a8ac541f4b8931c1f4f8e43aab0ccba04c22a15ab536e077e769aa8f08b
Timestamp: 1759876768 Timestamp [UCT]: 2025-10-07 22:39:28 Age [y:d:h:m:s]: 00:089:21:54:47
Block: 1385024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64412 RingCT/type: yes/0
Extra: 010e0d1a8ac541f4b8931c1f4f8e43aab0ccba04c22a15ab536e077e769aa8f08b021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4cfbe0b1741cd7df3e1f539c98ec5fd59b3672b52049369461db21868a708d5 0.600000000000 1873181 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": 1385034, "vin": [ { "gen": { "height": 1385024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4cfbe0b1741cd7df3e1f539c98ec5fd59b3672b52049369461db21868a708d5" } } ], "extra": [ 1, 14, 13, 26, 138, 197, 65, 244, 184, 147, 28, 31, 79, 142, 67, 170, 176, 204, 186, 4, 194, 42, 21, 171, 83, 110, 7, 126, 118, 154, 168, 240, 139, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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