Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34fd445d3ed38c1ccdcf228624f95ad472e137be8ed3ac3192b9afd6d7ef49d8

Tx prefix hash: c830544b9960bbb9105b917bb606aa82e360726b481c83d1c28a829e7977754c
Tx public key: 4263bc3880a31b5f0b8964a064847df25d7b8f81cec0f372302006304187089c
Timestamp: 1742527695 Timestamp [UTC]: 2025-03-21 03:28:15 Age [y:d:h:m:s]: 01:054:03:59:09
Block: 1243863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289579 RingCT/type: yes/0
Extra: 014263bc3880a31b5f0b8964a064847df25d7b8f81cec0f372302006304187089c021100000001bfa77623000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f35100bc150804b6f954bde4b07932fd47650918ac5845000a22309d28d5ea3 0.000600000000 1730854 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": 1243873, "vin": [ { "gen": { "height": 1243863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f35100bc150804b6f954bde4b07932fd47650918ac5845000a22309d28d5ea3" } } ], "extra": [ 1, 66, 99, 188, 56, 128, 163, 27, 95, 11, 137, 100, 160, 100, 132, 125, 242, 93, 123, 143, 129, 206, 192, 243, 114, 48, 32, 6, 48, 65, 135, 8, 156, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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: