Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2574238aa95bf992299216d2f8cbe928c1642cae130a4f3919f2c7c2de553803

Tx prefix hash: 41c1ba0eba8d57e43a29422a8470ce896d73f630d4f13b2323b3e9d4adf1c70b
Tx public key: 242e91497cf7e533db7c7544e831667d904fa63e3d47236587eb69735b06b3f8
Timestamp: 1759057194 Timestamp [UCT]: 2025-09-28 10:59:54 Age [y:d:h:m:s]: 00:009:22:56:58
Block: 1378234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7126 RingCT/type: yes/0
Extra: 01242e91497cf7e533db7c7544e831667d904fa63e3d47236587eb69735b06b3f8021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c767b2e0ced34cfc581c5c9e218832234f6d6a43d9ac92cb6527973e6e3a0d93 0.600000000000 1866329 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": 1378244, "vin": [ { "gen": { "height": 1378234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c767b2e0ced34cfc581c5c9e218832234f6d6a43d9ac92cb6527973e6e3a0d93" } } ], "extra": [ 1, 36, 46, 145, 73, 124, 247, 229, 51, 219, 124, 117, 68, 232, 49, 102, 125, 144, 79, 166, 62, 61, 71, 35, 101, 135, 235, 105, 115, 91, 6, 179, 248, 2, 17, 0, 0, 0, 4, 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