Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3905dc9fe2eeeb90111e8cbe66c66c3718f4699e6c3ed044fb2cc88914f34f6

Tx prefix hash: d52f1ab7e5ef6815801d9e6d2e52aee885c00e4542767d8b6160989ee4c920a7
Tx public key: d0ea325d65cf1e36e368c36aac325b31cbd2bbb75074881a236228a8e55fa718
Timestamp: 1742545907 Timestamp [UCT]: 2025-03-21 08:31:47 Age [y:d:h:m:s]: 00:289:07:42:21
Block: 1244008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204583 RingCT/type: yes/0
Extra: 01d0ea325d65cf1e36e368c36aac325b31cbd2bbb75074881a236228a8e55fa718021100000002f8f51409000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 390542ef87d69ccf84661c5c0876d80367dce7f3b93349d451578346594cc52c 0.600000000000 1730999 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": 1244018, "vin": [ { "gen": { "height": 1244008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "390542ef87d69ccf84661c5c0876d80367dce7f3b93349d451578346594cc52c" } } ], "extra": [ 1, 208, 234, 50, 93, 101, 207, 30, 54, 227, 104, 195, 106, 172, 50, 91, 49, 203, 210, 187, 183, 80, 116, 136, 26, 35, 98, 40, 168, 229, 95, 167, 24, 2, 17, 0, 0, 0, 2, 248, 245, 20, 9, 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