Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324ed1d02b06776c2fd75ea758d21a8a234aa8bafb841cf0a2b608439d636b73

Tx prefix hash: 262280a5c961f9401ebe0c96853491ea9c9c3bddc56e4879e2b0141f8324d1ea
Tx public key: dc40831d38f8fc90ea53d94cbbcafff5c54a6ae585a44a5a47447eb380cfba00
Timestamp: 1765218122 Timestamp [UTC]: 2025-12-08 18:22:02 Age [y:d:h:m:s]: 00:083:20:38:28
Block: 1429309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 59827 RingCT/type: yes/0
Extra: 01dc40831d38f8fc90ea53d94cbbcafff5c54a6ae585a44a5a47447eb380cfba0002090000000cd48050ef00

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4a8761005c9ab4b2b1f3546c16b630db57d305ad4fc5833e30fb32ccb59b973 0.000600000000 1918034 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": 1429319, "vin": [ { "gen": { "height": 1429309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4a8761005c9ab4b2b1f3546c16b630db57d305ad4fc5833e30fb32ccb59b973" } } ], "extra": [ 1, 220, 64, 131, 29, 56, 248, 252, 144, 234, 83, 217, 76, 187, 202, 255, 245, 197, 74, 106, 229, 133, 164, 74, 90, 71, 68, 126, 179, 128, 207, 186, 0, 2, 9, 0, 0, 0, 12, 212, 128, 80, 239, 0 ], "rct_signatures": { "type": 0 } }


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