Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0330287db026e3d2354fc1653cb2baa9269dd7b8f4b59e5fbc1a6d982c3b0e6e

Tx prefix hash: b3c6d6e5896f204c9172ebd80865dca1919c8cf43d60b0492d41dc01ab93f802
Tx public key: 559ab6c1116508f367b23edb752b1a1b421b58326acc00a45f36eb06be70324b
Timestamp: 1738159280 Timestamp [UCT]: 2025-01-29 14:01:20 Age [y:d:h:m:s]: 00:142:19:47:18
Block: 1207683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101993 RingCT/type: yes/0
Extra: 01559ab6c1116508f367b23edb752b1a1b421b58326acc00a45f36eb06be70324b021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d9a1239bd40a2b976d5cd5fcd3063e904bf9bfd525b56253aa7e72c993a6b2d 0.600000000000 1694408 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": 1207693, "vin": [ { "gen": { "height": 1207683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d9a1239bd40a2b976d5cd5fcd3063e904bf9bfd525b56253aa7e72c993a6b2d" } } ], "extra": [ 1, 85, 154, 182, 193, 17, 101, 8, 243, 103, 178, 62, 219, 117, 43, 26, 27, 66, 27, 88, 50, 106, 204, 0, 164, 95, 54, 235, 6, 190, 112, 50, 75, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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