Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864cc172b525ce2f404ea7ebf897018be8c9d9c7ba3c14221c2bb3d94084685a

Tx prefix hash: cae7802036e0704ff4cbf83d02c06b25c4d1582e7a3b9c9da795a95397e27328
Tx public key: b2a90ff7381a8d3da66a3f15e30c626d2b135cd64ee9c4c9b74107f1029fc57f
Timestamp: 1579862164 Timestamp [UTC]: 2020-01-24 10:36:04 Age [y:d:h:m:s]: 06:303:03:05:18
Block: 51770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1631671 RingCT/type: yes/0
Extra: 01b2a90ff7381a8d3da66a3f15e30c626d2b135cd64ee9c4c9b74107f1029fc57f02110000002c4ac5aa02000000000000000000

1 output(s) for total of 0.413490303497 xmr

stealth address amount amount idx tag
00: 0d967be6e202cfa00de080a51f685dd8a6904f67e02e0adfe30145500667f668 0.413490303497 96038 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": 51780, "vin": [ { "gen": { "height": 51770 } } ], "vout": [ { "amount": 413490303497, "target": { "key": "0d967be6e202cfa00de080a51f685dd8a6904f67e02e0adfe30145500667f668" } } ], "extra": [ 1, 178, 169, 15, 247, 56, 26, 141, 61, 166, 106, 63, 21, 227, 12, 98, 109, 43, 19, 92, 214, 78, 233, 196, 201, 183, 65, 7, 241, 2, 159, 197, 127, 2, 17, 0, 0, 0, 44, 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) | monero version: