Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aefda6d65088b88d4636795d12f1adfba7934367d6f53d4546c45f553d3e7663

Tx prefix hash: bfd263bd3ce4d24ccd9d7e08ba966e6b594f4cd042e2a621a115c6f966370b0a
Tx public key: a31a0c9a1f90ffc6cf2fb0b8398bd97c3f09046c42ac49ed1e5e9b478f31146d
Timestamp: 1760475604 Timestamp [UCT]: 2025-10-14 21:00:04 Age [y:d:h:m:s]: 00:028:12:51:32
Block: 1390001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20431 RingCT/type: yes/0
Extra: 01a31a0c9a1f90ffc6cf2fb0b8398bd97c3f09046c42ac49ed1e5e9b478f31146d0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8244e9ef37f152dbf169297c85a5e25f1962d35b6be8139e6ef5574bf264ea7 0.600000000000 1878232 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": 1390011, "vin": [ { "gen": { "height": 1390001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8244e9ef37f152dbf169297c85a5e25f1962d35b6be8139e6ef5574bf264ea7" } } ], "extra": [ 1, 163, 26, 12, 154, 31, 144, 255, 198, 207, 47, 176, 184, 57, 139, 217, 124, 63, 9, 4, 108, 66, 172, 73, 237, 30, 94, 155, 71, 143, 49, 20, 109, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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