Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec1cf056dfb419b1959f6eae58a7e6166d0c8ebc5b34e10d9c477a7a87a58001

Tx prefix hash: 681546ac410f7b7a6abe784119ce29123c1905a062dabc97b96bfc307d6cc3f9
Tx public key: e5a5e02020c1b4caa07e060b7a210a7dd886937fc6c6e48a2c29499ea468e505
Timestamp: 1761419308 Timestamp [UTC]: 2025-10-25 19:08:28 Age [y:d:h:m:s]: 00:302:09:55:37
Block: 1397831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221889 RingCT/type: yes/0
Extra: 01e5a5e02020c1b4caa07e060b7a210a7dd886937fc6c6e48a2c29499ea468e505021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f0cc17b5d079b8e3824fb2a53077decdcfa06d4718c2cb1c84bceb96541a88a9 0.000600000000 1886122 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": 1397841, "vin": [ { "gen": { "height": 1397831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0cc17b5d079b8e3824fb2a53077decdcfa06d4718c2cb1c84bceb96541a88a9" } } ], "extra": [ 1, 229, 165, 224, 32, 32, 193, 180, 202, 160, 126, 6, 11, 122, 33, 10, 125, 216, 134, 147, 127, 198, 198, 228, 138, 44, 41, 73, 158, 164, 104, 229, 5, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: