Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94a7616ae7cd8728b6caa654c6d565f4994fa34c8225dff488ae89fc058cac9a

Tx prefix hash: e52e1e1a60996117c9f61ead959c7515e3715e2eb0f1d1b4edc037bdf125c841
Tx public key: dcf726d049bcbce9e58ae30fb60cb86e43484e5b3cf1e176a4fb4bad3ee5d123
Timestamp: 1703833489 Timestamp [UTC]: 2023-12-29 07:04:49 Age [y:d:h:m:s]: 02:238:14:07:08
Block: 923524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695957 RingCT/type: yes/0
Extra: 01dcf726d049bcbce9e58ae30fb60cb86e43484e5b3cf1e176a4fb4bad3ee5d123021100000003ad5694ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3d1ea90370fe75067b3166ceb6ac6c3e20f6abf356a3f13ed90abc325ae515af 0.000600000000 1381256 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": 923534, "vin": [ { "gen": { "height": 923524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d1ea90370fe75067b3166ceb6ac6c3e20f6abf356a3f13ed90abc325ae515af" } } ], "extra": [ 1, 220, 247, 38, 208, 73, 188, 188, 233, 229, 138, 227, 15, 182, 12, 184, 110, 67, 72, 78, 91, 60, 241, 225, 118, 164, 251, 75, 173, 62, 229, 209, 35, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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: