Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ca3c7c9f3ab23fe45a5d6893fea9e92f4c9a15044cbb9d8701efba7c489dbcc

Tx prefix hash: 78581a1cbc8246838f23f2391b1f0c9d0c8bef1cf7477fc68ef61b4f80ba379d
Tx public key: c478dbc0ae9bddcc553af81e49912ae4d6ecfb89f7b01a402a8ed6f30f110e3d
Timestamp: 1759245232 Timestamp [UCT]: 2025-09-30 15:13:52 Age [y:d:h:m:s]: 00:100:16:39:50
Block: 1379797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72111 RingCT/type: yes/0
Extra: 01c478dbc0ae9bddcc553af81e49912ae4d6ecfb89f7b01a402a8ed6f30f110e3d021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c896ff3f5e0d8681e784d90c307cc374b592295c7446c1dac69745f18364b7f9 0.600000000000 1867906 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": 1379807, "vin": [ { "gen": { "height": 1379797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c896ff3f5e0d8681e784d90c307cc374b592295c7446c1dac69745f18364b7f9" } } ], "extra": [ 1, 196, 120, 219, 192, 174, 155, 221, 204, 85, 58, 248, 30, 73, 145, 42, 228, 214, 236, 251, 137, 247, 176, 26, 64, 42, 142, 214, 243, 15, 17, 14, 61, 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