Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c574a0e137732fcc5c635c6d70921ac63d06751aa58d642e183a2d71b9016c

Tx prefix hash: 89b9110d1b4cfd18b6a3eb295321a8d46e1ae1de05665ba00fd5390078058938
Tx public key: 53694f696a7a8fd4426ff7b2d0de00ddb760c328de2d50a1fec9e3e997c25f65
Timestamp: 1713093721 Timestamp [UTC]: 2024-04-14 11:22:01 Age [y:d:h:m:s]: 02:219:16:13:36
Block: 1000281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 682089 RingCT/type: yes/0
Extra: 0153694f696a7a8fd4426ff7b2d0de00ddb760c328de2d50a1fec9e3e997c25f6502110000001259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b22a818c4a282ad6cdc59954736840a12074c135d870877e18efb9c21a92346e 0.000600000000 1460777 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": 1000291, "vin": [ { "gen": { "height": 1000281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b22a818c4a282ad6cdc59954736840a12074c135d870877e18efb9c21a92346e" } } ], "extra": [ 1, 83, 105, 79, 105, 106, 122, 143, 212, 66, 111, 247, 178, 208, 222, 0, 221, 183, 96, 195, 40, 222, 45, 80, 161, 254, 201, 227, 233, 151, 194, 95, 101, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 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) | monero version: