Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 256bd7c2ee82b7b5a8209ea20ea2300b15cbb4c989eaf93a2fd706370e81d9a8

Tx prefix hash: e8c037fc0695905fbae6b1f6483e7e34a97af0123d6d0e3c714402a2dca620b4
Tx public key: 04ef70db417f85a4d9fd48e792a4ba573374bc38a98a5c70222c7573f9df9e72
Timestamp: 1759574127 Timestamp [UCT]: 2025-10-04 10:35:27 Age [y:d:h:m:s]: 00:091:18:26:04
Block: 1382528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65717 RingCT/type: yes/0
Extra: 0104ef70db417f85a4d9fd48e792a4ba573374bc38a98a5c70222c7573f9df9e7202110000000c97baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5c98720ecae3848f4434f5b004f8904dc9856a3b2bc7a80d8bd7539c56d14e1 0.600000000000 1870663 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": 1382538, "vin": [ { "gen": { "height": 1382528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5c98720ecae3848f4434f5b004f8904dc9856a3b2bc7a80d8bd7539c56d14e1" } } ], "extra": [ 1, 4, 239, 112, 219, 65, 127, 133, 164, 217, 253, 72, 231, 146, 164, 186, 87, 51, 116, 188, 56, 169, 138, 92, 112, 34, 44, 117, 115, 249, 223, 158, 114, 2, 17, 0, 0, 0, 12, 151, 186, 249, 34, 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