Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488a42b3c7627baa3fe4d0ff07a5f2ea14d8ef35b4da42ee2be813ea249814bd

Tx prefix hash: 40cab16b383dd2ef34d69f4b17ec1c900524bcdf8712ea41dcc02f4cf8b39a36
Tx public key: e66ab610b26068ab8afef813a3321769275855776023ca702f602a1f46105d6e
Timestamp: 1772016726 Timestamp [UTC]: 2026-02-25 10:52:06 Age [y:d:h:m:s]: 00:266:19:17:41
Block: 1485477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196212 RingCT/type: yes/0
Extra: 01e66ab610b26068ab8afef813a3321769275855776023ca702f602a1f46105d6e02110000000ff188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f61b37b24ddf23d71d7f5ea800ad27d9f80ef7863e9fe10ec00895baff4e035e 0.000600000000 1974913 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": 1485487, "vin": [ { "gen": { "height": 1485477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f61b37b24ddf23d71d7f5ea800ad27d9f80ef7863e9fe10ec00895baff4e035e" } } ], "extra": [ 1, 230, 106, 182, 16, 178, 96, 104, 171, 138, 254, 248, 19, 163, 50, 23, 105, 39, 88, 85, 119, 96, 35, 202, 112, 47, 96, 42, 31, 70, 16, 93, 110, 2, 17, 0, 0, 0, 15, 241, 136, 200, 168, 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: