Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d85f27991f7b0e655d43930ffe49efee7fefa1380d43aed25b824b9f859fb207

Tx prefix hash: b6bae4d6443817824e9bfe88a0d19c2e2e86fc425187336a792dfc163ffb1b5a
Tx public key: 28aa5f6fd864a483d5f539779181bce8eb5f92f450e37d69391733e54d73f50f
Timestamp: 1763176624 Timestamp [UCT]: 2025-11-15 03:17:04 Age [y:d:h:m:s]: 00:046:00:19:42
Block: 1412389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32944 RingCT/type: yes/0
Extra: 0128aa5f6fd864a483d5f539779181bce8eb5f92f450e37d69391733e54d73f50f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98e9075b40000ce475e041bcb7a1c501c028c405970ac71bcb4ab099e279914 0.600000000000 1900856 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": 1412399, "vin": [ { "gen": { "height": 1412389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98e9075b40000ce475e041bcb7a1c501c028c405970ac71bcb4ab099e279914" } } ], "extra": [ 1, 40, 170, 95, 111, 216, 100, 164, 131, 213, 245, 57, 119, 145, 129, 188, 232, 235, 95, 146, 244, 80, 227, 125, 105, 57, 23, 51, 229, 77, 115, 245, 15, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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