Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51804270b76e679c834abd34e35c075bdba36dff25fe0a1dd26bf2a49646cbe1

Tx prefix hash: d6f23aaffdae8bf0ce4582e7e80a06251961986a1d0dd41c1cc823f89868924d
Tx public key: 8f387c228e3ba82c7f3294c030f853e52dbd24ed80b02f96ecbe9543fd5cc6dc
Timestamp: 1706810201 Timestamp [UTC]: 2024-02-01 17:56:41 Age [y:d:h:m:s]: 02:292:09:22:29
Block: 948187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734170 RingCT/type: yes/0
Extra: 018f387c228e3ba82c7f3294c030f853e52dbd24ed80b02f96ecbe9543fd5cc6dc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: be382324cb6433713e3074023fbff55667e43e85469c09d2c17d89d58d354a31 0.000600000000 1406559 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": 948197, "vin": [ { "gen": { "height": 948187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be382324cb6433713e3074023fbff55667e43e85469c09d2c17d89d58d354a31" } } ], "extra": [ 1, 143, 56, 124, 34, 142, 59, 168, 44, 127, 50, 148, 192, 48, 248, 83, 229, 45, 189, 36, 237, 128, 176, 47, 150, 236, 190, 149, 67, 253, 92, 198, 220, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: