Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66329065bd5ff6e587c8907e0d9e2864c698c4ae73c28f5014cfd3bd1f2c2846

Tx prefix hash: 665265308f91f73e0ecb83f090bdab38eb1642a40c7dbbd01b46f49b98a00496
Tx public key: dbd92afe6e2faaefc9b76758b8bf6fdea7069a0ab9799cb4fb9750a8cd4e3cdb
Timestamp: 1765676236 Timestamp [UCT]: 2025-12-14 01:37:16 Age [y:d:h:m:s]: 00:022:22:50:44
Block: 1433092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16461 RingCT/type: yes/0
Extra: 01dbd92afe6e2faaefc9b76758b8bf6fdea7069a0ab9799cb4fb9750a8cd4e3cdb02110000000c70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369d4254646556ceb35420d88dd076531ed9ea8c3cc65417b89da5b6e40c34e8 0.600000000000 1921871 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": 1433102, "vin": [ { "gen": { "height": 1433092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369d4254646556ceb35420d88dd076531ed9ea8c3cc65417b89da5b6e40c34e8" } } ], "extra": [ 1, 219, 217, 42, 254, 110, 47, 170, 239, 201, 183, 103, 88, 184, 191, 111, 222, 167, 6, 154, 10, 185, 121, 156, 180, 251, 151, 80, 168, 205, 78, 60, 219, 2, 17, 0, 0, 0, 12, 112, 96, 157, 3, 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