Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffcce855c85d9ea5dd6bc917101b84f03eb82876a4cde84005dd349d10bf4d6a

Tx prefix hash: e2b84e37454b58880a6e47efa5ae431a9145d468e17aa9b87a9decb3123e05cc
Tx public key: 269f996c4fdd713cf3b846827b73bb1268bab5af10dcbafff53c4932a3e9d37e
Timestamp: 1746833114 Timestamp [UCT]: 2025-05-09 23:25:14 Age [y:d:h:m:s]: 00:186:10:26:22
Block: 1279483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130949 RingCT/type: yes/0
Extra: 01269f996c4fdd713cf3b846827b73bb1268bab5af10dcbafff53c4932a3e9d37e0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 771f8313d976bcc9d32c890cb07f85e1f100f62fcc21a8b3465bf3de976adc0f 0.600000000000 1766860 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": 1279493, "vin": [ { "gen": { "height": 1279483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "771f8313d976bcc9d32c890cb07f85e1f100f62fcc21a8b3465bf3de976adc0f" } } ], "extra": [ 1, 38, 159, 153, 108, 79, 221, 113, 60, 243, 184, 70, 130, 123, 115, 187, 18, 104, 186, 181, 175, 16, 220, 186, 255, 245, 60, 73, 50, 163, 233, 211, 126, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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