Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010bd5e76c1c691b52c1f1bcc8e4b9971dc3e9408af43b402f5a01262335a02b

Tx prefix hash: 2bdd52ef1e92d196ec651af89dafbb3105eda1b5b5f737212ca4a49acd4b15a0
Tx public key: 839e7a3f12108a9176d0d919ee1d7d442738fe43dfd2cda3f42a4b2778375078
Timestamp: 1710002924 Timestamp [UTC]: 2024-03-09 16:48:44 Age [y:d:h:m:s]: 02:168:14:50:30
Block: 974682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645854 RingCT/type: yes/0
Extra: 01839e7a3f12108a9176d0d919ee1d7d442738fe43dfd2cda3f42a4b27783750780211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb0bdd1d4e11dd00fdead58bb9b323670b6ebdeb23b2d9c0a90ebce7eae4baf7 0.000600000000 1434641 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": 974692, "vin": [ { "gen": { "height": 974682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0bdd1d4e11dd00fdead58bb9b323670b6ebdeb23b2d9c0a90ebce7eae4baf7" } } ], "extra": [ 1, 131, 158, 122, 63, 18, 16, 138, 145, 118, 208, 217, 25, 238, 29, 125, 68, 39, 56, 254, 67, 223, 210, 205, 163, 244, 42, 75, 39, 120, 55, 80, 120, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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: