Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d59952af4c3a1d52376faa718cae094e9da4fec348e5224146f388af8021c527

Tx prefix hash: bd4ec4a0c51ead67539196f8f7bc5f78a7654e06bf30bf122642a9d70f1dda37
Tx public key: a06839867fb76a14824c33d4f7cca14d75e1c57c04e636ae6a65a2b82f5ab165
Timestamp: 1700942829 Timestamp [UTC]: 2023-11-25 20:07:09 Age [y:d:h:m:s]: 02:362:12:19:13
Block: 899561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783933 RingCT/type: yes/0
Extra: 01a06839867fb76a14824c33d4f7cca14d75e1c57c04e636ae6a65a2b82f5ab16502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.000641772296 xmr

stealth address amount amount idx tag
00: b972ed523ae552226b2e857b90eccd47bc6e621a7f1562e968a0b2c46f6104d5 0.000641772296 1356020 of 0 -

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": 899571, "vin": [ { "gen": { "height": 899561 } } ], "vout": [ { "amount": 641772296, "target": { "key": "b972ed523ae552226b2e857b90eccd47bc6e621a7f1562e968a0b2c46f6104d5" } } ], "extra": [ 1, 160, 104, 57, 134, 127, 183, 106, 20, 130, 76, 51, 212, 247, 204, 161, 77, 117, 225, 197, 124, 4, 230, 54, 174, 106, 101, 162, 184, 47, 90, 177, 101, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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: