Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c010dcb61a20eceda083060b8b80c18c01da5168b391300fc044392bc5c58831

Tx prefix hash: 8064d72cbc6685059fd614c0197ae1e805769cd283fe3b367db77c6410ac45f1
Tx public key: d7b5e1731405c219fce5ce5009cb1d149037c93f5e663dcda75f2816cb87c6ef
Timestamp: 1751024369 Timestamp [UCT]: 2025-06-27 11:39:29 Age [y:d:h:m:s]: 00:140:02:01:22
Block: 1313823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98155 RingCT/type: yes/0
Extra: 01d7b5e1731405c219fce5ce5009cb1d149037c93f5e663dcda75f2816cb87c6ef0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9790c522f9b18d72e4e26ea89ea8f0d13fa217340ce8fb6dc49fe9da53b7756 0.600000000000 1801466 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": 1313833, "vin": [ { "gen": { "height": 1313823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9790c522f9b18d72e4e26ea89ea8f0d13fa217340ce8fb6dc49fe9da53b7756" } } ], "extra": [ 1, 215, 181, 225, 115, 20, 5, 194, 25, 252, 229, 206, 80, 9, 203, 29, 20, 144, 55, 201, 63, 94, 102, 61, 205, 167, 95, 40, 22, 203, 135, 198, 239, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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