Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ffbf0eefb2f846f03aa5b3adc91e58a71bc1ad4d33606f06814ac9533d89e4

Tx prefix hash: c4cd8af3ba9dc00a4bd89916017712259f9dca2c586d03679ff5d132d514926a
Tx public key: 515704eb784c3e0e76d6aa3f46d9663bbc7c809dab6de9485f5a5b58320f2bf0
Timestamp: 1756366765 Timestamp [UCT]: 2025-08-28 07:39:25 Age [y:d:h:m:s]: 00:078:09:28:26
Block: 1356135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55946 RingCT/type: yes/0
Extra: 01515704eb784c3e0e76d6aa3f46d9663bbc7c809dab6de9485f5a5b58320f2bf00211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac10a6e4addf26a71715b65cf59338c13879475bd98289beb5ba9f1baeb7a53 0.600000000000 1844140 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": 1356145, "vin": [ { "gen": { "height": 1356135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac10a6e4addf26a71715b65cf59338c13879475bd98289beb5ba9f1baeb7a53" } } ], "extra": [ 1, 81, 87, 4, 235, 120, 76, 62, 14, 118, 214, 170, 63, 70, 217, 102, 59, 188, 124, 128, 157, 171, 109, 233, 72, 95, 90, 91, 88, 50, 15, 43, 240, 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