Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23838d69b0c161bf318e2d2498c9d53240fa2b6e2e1220de6b7d7c8255b2cf3e

Tx prefix hash: 45e13e8cc2f9d36af00a56f1c82816bef7f80efff8c6710e62c5a6faa4837568
Tx public key: fb6cf6b5a52be50db446bc7aa2362156ef6c0443873c12f5c97b2a4018c741a7
Timestamp: 1708361508 Timestamp [UTC]: 2024-02-19 16:51:48 Age [y:d:h:m:s]: 02:016:04:34:54
Block: 961064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531140 RingCT/type: yes/0
Extra: 01fb6cf6b5a52be50db446bc7aa2362156ef6c0443873c12f5c97b2a4018c741a70211000000080011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0d983e29c2aef043ba9e7538207ad194b0b60f803a769704b1bbff5f2e1b5b30 0.000600000000 1420651 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": 961074, "vin": [ { "gen": { "height": 961064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d983e29c2aef043ba9e7538207ad194b0b60f803a769704b1bbff5f2e1b5b30" } } ], "extra": [ 1, 251, 108, 246, 181, 165, 43, 229, 13, 180, 70, 188, 122, 162, 54, 33, 86, 239, 108, 4, 67, 135, 60, 18, 245, 201, 123, 42, 64, 24, 199, 65, 167, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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