Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5756ee552968dce29b286b41ef31ae2642604d187a0428e74b38d85501c6794c

Tx prefix hash: f8f2be402f56395e79ddc41184b27f4c14b6d3fd6930cb3b5fce6f91818c1885
Tx public key: 035ba66f789ef48083e1497ad3c059dd6bd53f0cfc5ad9243b2a8227d1f5cf5a
Timestamp: 1759134633 Timestamp [UCT]: 2025-09-29 08:30:33 Age [y:d:h:m:s]: 00:008:14:14:01
Block: 1378878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6149 RingCT/type: yes/0
Extra: 01035ba66f789ef48083e1497ad3c059dd6bd53f0cfc5ad9243b2a8227d1f5cf5a021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8285ca5764b724da467e3d35dd67a700d53aac5694cfb2a84dc414ec85bcc4e 0.600000000000 1866975 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": 1378888, "vin": [ { "gen": { "height": 1378878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8285ca5764b724da467e3d35dd67a700d53aac5694cfb2a84dc414ec85bcc4e" } } ], "extra": [ 1, 3, 91, 166, 111, 120, 158, 244, 128, 131, 225, 73, 122, 211, 192, 89, 221, 107, 213, 63, 12, 252, 90, 217, 36, 59, 42, 130, 39, 209, 245, 207, 90, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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