Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a49b00bc53bf5a5ee3c0a11b9f7f049d749d67e9ab7e3ad87f504ae8fdc1b9c1

Tx prefix hash: 587bf218ca6b6b84a5a1a93f44b1d4270acfe0856eb8f83ebe0102bdbcd83b53
Tx public key: 2bf05f9ed261dd857eb2f97c45a65e69e8491d11dcf3486bdede717576d1ee41
Timestamp: 1749253658 Timestamp [UTC]: 2025-06-06 23:47:38 Age [y:d:h:m:s]: 00:342:14:58:36
Block: 1299520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234908 RingCT/type: yes/0
Extra: 012bf05f9ed261dd857eb2f97c45a65e69e8491d11dcf3486bdede717576d1ee4102110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: da2f41dc153d7dedc5c06ebffdb2012a7fdb25fba43bd580a0f1241112c74c3c 0.000600000000 1787057 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": 1299530, "vin": [ { "gen": { "height": 1299520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da2f41dc153d7dedc5c06ebffdb2012a7fdb25fba43bd580a0f1241112c74c3c" } } ], "extra": [ 1, 43, 240, 95, 158, 210, 97, 221, 133, 126, 178, 249, 124, 69, 166, 94, 105, 232, 73, 29, 17, 220, 243, 72, 107, 222, 222, 113, 117, 118, 209, 238, 65, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: