Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2504c1f7c45aa6d2285eac8ae5510fb08679e8e39c11cb46a5510acf69fc5de

Tx prefix hash: 3c88a3b483e13241d9692af63c7aa7266ff36f51f5f298e34fb3be5bccfe1800
Tx public key: 53221f6bb26ae4944e4a876352d3f5e128719590ef47b370734c9e63500a89fb
Timestamp: 1760777328 Timestamp [UCT]: 2025-10-18 08:48:48 Age [y:d:h:m:s]: 00:022:10:52:05
Block: 1392522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16061 RingCT/type: yes/0
Extra: 0153221f6bb26ae4944e4a876352d3f5e128719590ef47b370734c9e63500a89fb0211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04f2c19237e8068fb7429cd3b98bbf61a9d7998203376ba9726390e2f3c23c09 0.600000000000 1880773 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": 1392532, "vin": [ { "gen": { "height": 1392522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04f2c19237e8068fb7429cd3b98bbf61a9d7998203376ba9726390e2f3c23c09" } } ], "extra": [ 1, 83, 34, 31, 107, 178, 106, 228, 148, 78, 74, 135, 99, 82, 211, 245, 225, 40, 113, 149, 144, 239, 71, 179, 112, 115, 76, 158, 99, 80, 10, 137, 251, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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