Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b4147e9fdda238ec7699e9c79c293cae1fcf4b968ecabfa47a49cd82c322d3

Tx prefix hash: 26a73794ce0f52cd5947545f617570875847463b1ac7861da179a9fcf7ada723
Tx public key: d066c6e2066c833ab369f899a9840986d28d83353f65ce6fb6912e5c0ef7234a
Timestamp: 1738448057 Timestamp [UTC]: 2025-02-01 22:14:17 Age [y:d:h:m:s]: 01:138:15:54:33
Block: 1210064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353824 RingCT/type: yes/0
Extra: 01d066c6e2066c833ab369f899a9840986d28d83353f65ce6fb6912e5c0ef7234a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 298423962a364834173a2328db42ae7d899e24bc0df3ab6b32eb4bfa0ba984b0 0.000600000000 1696811 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": 1210074, "vin": [ { "gen": { "height": 1210064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "298423962a364834173a2328db42ae7d899e24bc0df3ab6b32eb4bfa0ba984b0" } } ], "extra": [ 1, 208, 102, 198, 226, 6, 108, 131, 58, 179, 105, 248, 153, 169, 132, 9, 134, 210, 141, 131, 53, 63, 101, 206, 111, 182, 145, 46, 92, 14, 247, 35, 74, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: