Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4bfe2fc8136bffe06ffe0ab179619400dc852c4a4c157031bb4c5973a0dfa8

Tx prefix hash: 3a93d620520bdf37ad6a5e4482a18f0fcc8a96a8ce016e4e43f5db0df5eade5e
Tx public key: 94290b76d48194e9265e0c0e180bb273d1a58100c9c80a212d188b4c6c9ea5f6
Timestamp: 1737505130 Timestamp [UCT]: 2025-01-22 00:18:50 Age [y:d:h:m:s]: 00:333:08:06:50
Block: 1202489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235828 RingCT/type: yes/0
Extra: 0194290b76d48194e9265e0c0e180bb273d1a58100c9c80a212d188b4c6c9ea5f6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f24d815d7da18bf352d311f0a34db9c6b5b94ebc93c6170fbeb9efa9c83a72d 0.600000000000 1689154 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": 1202499, "vin": [ { "gen": { "height": 1202489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f24d815d7da18bf352d311f0a34db9c6b5b94ebc93c6170fbeb9efa9c83a72d" } } ], "extra": [ 1, 148, 41, 11, 118, 212, 129, 148, 233, 38, 94, 12, 14, 24, 11, 178, 115, 209, 165, 129, 0, 201, 200, 10, 33, 45, 24, 139, 76, 108, 158, 165, 246, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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