Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32d0abba87410e5bb91f4f16b4679187e4c1285c7f14f57ee5058a718d0caec0

Tx prefix hash: 5f82ee7f72548afa05fc4825092c5934ebd2dad3b3b02ccf691525d391d303db
Tx public key: cdb1ee030fdabe9415d7275a5ed0ee7a18e8f728079be9f3df0eb2da260161e6
Timestamp: 1743339264 Timestamp [UTC]: 2025-03-30 12:54:24 Age [y:d:h:m:s]: 01:147:15:56:35
Block: 1250554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369893 RingCT/type: yes/0
Extra: 01cdb1ee030fdabe9415d7275a5ed0ee7a18e8f728079be9f3df0eb2da260161e60211000000021a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd3b2cb2f14a04867fe74577913e9e0274cda0d0877950879db21fd881a0da13 0.000600000000 1737603 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": 1250564, "vin": [ { "gen": { "height": 1250554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd3b2cb2f14a04867fe74577913e9e0274cda0d0877950879db21fd881a0da13" } } ], "extra": [ 1, 205, 177, 238, 3, 15, 218, 190, 148, 21, 215, 39, 90, 94, 208, 238, 122, 24, 232, 247, 40, 7, 155, 233, 243, 223, 14, 178, 218, 38, 1, 97, 230, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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: