Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bdd9a8c8ea8b5d20c9bdfa12886e866a4312a3de33fcd037dfdccb30421ec9

Tx prefix hash: 61db368b029946b7828b222fe87fa3543fb0e364e015f37eb902dd0552c8a6de
Tx public key: 6bfb6ab24f73aed183c5781f7661963327cdfbea79bd1bdbe71447b96cc787f2
Timestamp: 1748774882 Timestamp [UTC]: 2025-06-01 10:48:02 Age [y:d:h:m:s]: 01:164:15:03:14
Block: 1295574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381478 RingCT/type: yes/0
Extra: 016bfb6ab24f73aed183c5781f7661963327cdfbea79bd1bdbe71447b96cc787f2021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1b64863b086e1791bf65d1d28b69284af0ece676e0a68c396fa638fb1fce0af1 0.000600000000 1783077 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": 1295584, "vin": [ { "gen": { "height": 1295574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b64863b086e1791bf65d1d28b69284af0ece676e0a68c396fa638fb1fce0af1" } } ], "extra": [ 1, 107, 251, 106, 178, 79, 115, 174, 209, 131, 197, 120, 31, 118, 97, 150, 51, 39, 205, 251, 234, 121, 189, 27, 219, 231, 20, 71, 185, 108, 199, 135, 242, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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: