Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42fe7683b1572cdeb65229d8b1041ec259f61eccc1c116a51784d1f1f72ac437

Tx prefix hash: dce6d6c0b6178c856558a7f9c9c1e2e6f94c96572174b2acc4b155ac704ddaa5
Tx public key: 754f0a7e49aac381bd2c02fb75677afda2a40dd3d963ac53452a38d945837788
Timestamp: 1763656929 Timestamp [UCT]: 2025-11-20 16:42:09 Age [y:d:h:m:s]: 00:033:04:03:03
Block: 1416357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23751 RingCT/type: yes/0
Extra: 01754f0a7e49aac381bd2c02fb75677afda2a40dd3d963ac53452a38d94583778802110000001370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c965702f6704724f21971e2a5bd5e5d8dff8fe6385af2b5f0a5c4bcb4e014e3 0.600000000000 1904876 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": 1416367, "vin": [ { "gen": { "height": 1416357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c965702f6704724f21971e2a5bd5e5d8dff8fe6385af2b5f0a5c4bcb4e014e3" } } ], "extra": [ 1, 117, 79, 10, 126, 73, 170, 195, 129, 189, 44, 2, 251, 117, 103, 122, 253, 162, 164, 13, 211, 217, 99, 172, 83, 69, 42, 56, 217, 69, 131, 119, 136, 2, 17, 0, 0, 0, 19, 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