Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f202aee9d40cf8277b8674b6fc4cc83d041cb44af55a51baf2f2863fe9c4af3

Tx prefix hash: ea9aebb4b380c2d682ec4fe3951723e1b5678ae4c18f1a08c96bd381c4d5aec7
Tx public key: bfb9d396276c6c1b113c06761aaeff022f462943c14a46a2a9db131bfc4bce65
Timestamp: 1617582738 Timestamp [UTC]: 2021-04-05 00:32:18 Age [y:d:h:m:s]: 05:231:22:04:41
Block: 233378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1450116 RingCT/type: yes/0
Extra: 01bfb9d396276c6c1b113c06761aaeff022f462943c14a46a2a9db131bfc4bce650211000000183634f08d000000000000000000

1 output(s) for total of 0.103448067680 xmr

stealth address amount amount idx tag
00: 9d4a9adc32c44baaf93d747775de8a411a2339787aa96fe4569f08224c3541c8 0.103448067680 484670 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": 233388, "vin": [ { "gen": { "height": 233378 } } ], "vout": [ { "amount": 103448067680, "target": { "key": "9d4a9adc32c44baaf93d747775de8a411a2339787aa96fe4569f08224c3541c8" } } ], "extra": [ 1, 191, 185, 211, 150, 39, 108, 108, 27, 17, 60, 6, 118, 26, 174, 255, 2, 47, 70, 41, 67, 193, 74, 70, 162, 169, 219, 19, 27, 252, 75, 206, 101, 2, 17, 0, 0, 0, 24, 54, 52, 240, 141, 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: