Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70885fa2be262ab91c58e2fc81e22e2e44ab6183c9bb3a53675c390ed0fd6dc

Tx prefix hash: 397e09a6986e88ae9a61c951749872610276079d354584d56ccfed1e2fd8df63
Tx public key: d519968c795c249ccb6f4cce932612e3d276ea664a0dc4a7c03a65800361da77
Timestamp: 1745387974 Timestamp [UTC]: 2025-04-23 05:59:34 Age [y:d:h:m:s]: 01:070:00:20:28
Block: 1267510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299394 RingCT/type: yes/0
Extra: 01d519968c795c249ccb6f4cce932612e3d276ea664a0dc4a7c03a65800361da770211000000096c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2961522c175500ec13945d522fb4de9af88a9e0e945148bd49678c5e9d777837 0.000600000000 1754739 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": 1267520, "vin": [ { "gen": { "height": 1267510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2961522c175500ec13945d522fb4de9af88a9e0e945148bd49678c5e9d777837" } } ], "extra": [ 1, 213, 25, 150, 140, 121, 92, 36, 156, 203, 111, 76, 206, 147, 38, 18, 227, 210, 118, 234, 102, 74, 13, 196, 167, 192, 58, 101, 128, 3, 97, 218, 119, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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: