Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e434e82bf2a3b2882b118e7b551fe7f13dc9de92e168a23872d0eedd1323ab

Tx prefix hash: 5b982264d9106d58a584d18a7b5846a4a53513b91aef2f52c9fb046dea6b222a
Tx public key: 6e669975075b3f1db94446503a9bde8ee0a748e05cb85a6d2308c4024b4aa531
Timestamp: 1743869063 Timestamp [UTC]: 2025-04-05 16:04:23 Age [y:d:h:m:s]: 01:040:04:06:51
Block: 1254944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279652 RingCT/type: yes/0
Extra: 016e669975075b3f1db94446503a9bde8ee0a748e05cb85a6d2308c4024b4aa5310211000000126c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d3a5db46af28648ebd9bc9201bb5fc79f5b3cecaebcbea7f17a87915033cdd3 0.000600000000 1742039 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": 1254954, "vin": [ { "gen": { "height": 1254944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d3a5db46af28648ebd9bc9201bb5fc79f5b3cecaebcbea7f17a87915033cdd3" } } ], "extra": [ 1, 110, 102, 153, 117, 7, 91, 63, 29, 185, 68, 70, 80, 58, 155, 222, 142, 224, 167, 72, 224, 92, 184, 90, 109, 35, 8, 196, 2, 75, 74, 165, 49, 2, 17, 0, 0, 0, 18, 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: