Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3feb5595df3498e39ac8fcdec6bbd06f3171f3af950650c8654596cd82e80c29

Tx prefix hash: 301e255a29b451af8b55dc971701589e8b6bf2ef013f270a5ae59de063e6793a
Tx public key: 9a3230d82550c4b6c2b4a3114d753d448fe5876abd731860392f9d9a4e6c278e
Timestamp: 1761717343 Timestamp [UCT]: 2025-10-29 05:55:43 Age [y:d:h:m:s]: 00:008:16:19:51
Block: 1400302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6203 RingCT/type: yes/0
Extra: 019a3230d82550c4b6c2b4a3114d753d448fe5876abd731860392f9d9a4e6c278e02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aae74f7ae9673ad9e6522b4a8c6240c633df4193ef01809cb5bed1305ca4d81 0.600000000000 1888609 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": 1400312, "vin": [ { "gen": { "height": 1400302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aae74f7ae9673ad9e6522b4a8c6240c633df4193ef01809cb5bed1305ca4d81" } } ], "extra": [ 1, 154, 50, 48, 216, 37, 80, 196, 182, 194, 180, 163, 17, 77, 117, 61, 68, 143, 229, 135, 106, 189, 115, 24, 96, 57, 47, 157, 154, 78, 108, 39, 142, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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