Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9ed554b69028dc24ab84e1357ea1e3d13409a99a2e718e2ea0bf6b461712d9

Tx prefix hash: 1a3b329014b955659ed92eab68ed97cad832972fbd2e47949cb5c37a86192e46
Tx public key: 6363e22e934b0bee379aa0700996af0f607e2fb55c8b094ceffd3942d341b7d8
Timestamp: 1578161750 Timestamp [UTC]: 2020-01-04 18:15:50 Age [y:d:h:m:s]: 06:045:14:47:30
Block: 38715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1440937 RingCT/type: yes/0
Extra: 016363e22e934b0bee379aa0700996af0f607e2fb55c8b094ceffd3942d341b7d80211000000154ac5aa02000000000000000000

1 output(s) for total of 0.456795674846 xmr

stealth address amount amount idx tag
00: d94d78684c0e3d0bbffe4293a9c05402c9afa34685d20c576a7db82ebff51178 0.456795674846 66211 of 0 -

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": 38725, "vin": [ { "gen": { "height": 38715 } } ], "vout": [ { "amount": 456795674846, "target": { "key": "d94d78684c0e3d0bbffe4293a9c05402c9afa34685d20c576a7db82ebff51178" } } ], "extra": [ 1, 99, 99, 226, 46, 147, 75, 11, 238, 55, 154, 160, 112, 9, 150, 175, 15, 96, 126, 47, 181, 92, 139, 9, 76, 239, 253, 57, 66, 211, 65, 183, 216, 2, 17, 0, 0, 0, 21, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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