Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bede0e4648b7470b5fa25af2350856b7acf05b278b86a8c63c30d39a08e04f7

Tx prefix hash: 947251b5f0a3dcb8bfee215b24c3d8fbed4ac7731991ad6c647f47ce7433d719
Tx public key: 05cf0f006ee92aacbbb3c3670d19948c51ea4edd3b615cdcb3f4897ca497defb
Timestamp: 1747490341 Timestamp [UCT]: 2025-05-17 13:59:01 Age [y:d:h:m:s]: 00:186:01:37:42
Block: 1284932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130678 RingCT/type: yes/0
Extra: 0105cf0f006ee92aacbbb3c3670d19948c51ea4edd3b615cdcb3f4897ca497defb0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cce0f6997077a12e8dfe7567809a7f3e6a644d3f13859b2eabd3656aeeec79d 0.600000000000 1772395 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": 1284942, "vin": [ { "gen": { "height": 1284932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cce0f6997077a12e8dfe7567809a7f3e6a644d3f13859b2eabd3656aeeec79d" } } ], "extra": [ 1, 5, 207, 15, 0, 110, 233, 42, 172, 187, 179, 195, 103, 13, 25, 148, 140, 81, 234, 78, 221, 59, 97, 92, 220, 179, 244, 137, 124, 164, 151, 222, 251, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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