Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e64b64122aa3d37bbaf1b72c0512eaddb6bf077da1cf19ab66917179713b0dac

Tx prefix hash: 492ef23f19bc9defc846d1d1ef538d81dbb1e087975e25a8f476a592f4000567
Tx public key: 310d74d5bd38cfdc941f555a91e41034d131821c486c0b19e537a5d3907c8f3c
Timestamp: 1585420969 Timestamp [UTC]: 2020-03-28 18:42:49 Age [y:d:h:m:s]: 06:239:11:46:43
Block: 89223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1594271 RingCT/type: yes/0
Extra: 01310d74d5bd38cfdc941f555a91e41034d131821c486c0b19e537a5d3907c8f3c02110000002f39be35fb000000000000000000

1 output(s) for total of 0.310719092067 xmr

stealth address amount amount idx tag
00: d8b3b53e3be8c14f6606c21d2dd9e49abef624cf67e40f94536c852c49516a53 0.310719092067 160139 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": 89233, "vin": [ { "gen": { "height": 89223 } } ], "vout": [ { "amount": 310719092067, "target": { "key": "d8b3b53e3be8c14f6606c21d2dd9e49abef624cf67e40f94536c852c49516a53" } } ], "extra": [ 1, 49, 13, 116, 213, 189, 56, 207, 220, 148, 31, 85, 90, 145, 228, 16, 52, 209, 49, 130, 28, 72, 108, 11, 25, 229, 55, 165, 211, 144, 124, 143, 60, 2, 17, 0, 0, 0, 47, 57, 190, 53, 251, 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: