Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055662d78fee09d88363353427afadfc7caba6868538b121754d125b8140c13b

Tx prefix hash: 389b281a3c0292e0f54d0aadad097665b2128292211af34267067f9753b87bb6
Tx public key: 784637df786dcb2cdf32b0b5e1c4b60d6f6c6ef8b0de9b0a84d1c8b09f8dc4d8
Timestamp: 1767247459 Timestamp [UTC]: 2026-01-01 06:04:19 Age [y:d:h:m:s]: 00:044:21:52:31
Block: 1446122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 31961 RingCT/type: yes/0
Extra: 01784637df786dcb2cdf32b0b5e1c4b60d6f6c6ef8b0de9b0a84d1c8b09f8dc4d802090000000af3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b83ecfb8b45f3c7309897151485e56a6c44839629a83ca8bf7e70da8aca22d2f 0.000600000000 1935074 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 dinastycoin-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": 1446132, "vin": [ { "gen": { "height": 1446122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b83ecfb8b45f3c7309897151485e56a6c44839629a83ca8bf7e70da8aca22d2f" } } ], "extra": [ 1, 120, 70, 55, 223, 120, 109, 203, 44, 223, 50, 176, 181, 225, 196, 182, 13, 111, 108, 110, 248, 176, 222, 155, 10, 132, 209, 200, 176, 159, 141, 196, 216, 2, 9, 0, 0, 0, 10, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369