Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b016d7f91a5fc19ad709fc512fc4f1d49b5fb2f236141330a58739c17bc7bc9b

Tx prefix hash: 0adc91b69d0b6dc176e815d366fc5ed5689db6e6490a0cd59841a49be026efff
Tx public key: e65cd2169a738d1515b520310d941f7d216919e5f063cd2814d10660cbe38902
Timestamp: 1724059879 Timestamp [UTC]: 2024-08-19 09:31:19 Age [y:d:h:m:s]: 02:090:23:25:10
Block: 1091225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589791 RingCT/type: yes/0
Extra: 01e65cd2169a738d1515b520310d941f7d216919e5f063cd2814d10660cbe3890202110000000891e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d9a13ce06d628ad8f1f7f5052aff65bf7250fd6851d96dcaa8357c73432b7a2e 0.000600000000 1565856 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": 1091235, "vin": [ { "gen": { "height": 1091225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9a13ce06d628ad8f1f7f5052aff65bf7250fd6851d96dcaa8357c73432b7a2e" } } ], "extra": [ 1, 230, 92, 210, 22, 154, 115, 141, 21, 21, 181, 32, 49, 13, 148, 31, 125, 33, 105, 25, 229, 240, 99, 205, 40, 20, 209, 6, 96, 203, 227, 137, 2, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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: