Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 658689c0eeb5364822fe93ed64f31b2a0466a840c0aabeb2e704be8b0e760085

Tx prefix hash: 231c9bc985dd11beaf8b4ad9d64e36b40eb2434612b09379c78158fed41c4362
Tx public key: 71f551d3c916ee9b58ad2bd8c6aa09d693876ba8fe1ce7235c9d860e93e94ac1
Timestamp: 1768170456 Timestamp [UTC]: 2026-01-11 22:27:36 Age [y:d:h:m:s]: 00:225:11:40:10
Block: 1453771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166841 RingCT/type: yes/0
Extra: 0171f551d3c916ee9b58ad2bd8c6aa09d693876ba8fe1ce7235c9d860e93e94ac1021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b92ba6f3e601b319e315b6effacbf390091e57e082dcbcd0518e0757fdc05963 0.000600000000 1942849 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": 1453781, "vin": [ { "gen": { "height": 1453771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b92ba6f3e601b319e315b6effacbf390091e57e082dcbcd0518e0757fdc05963" } } ], "extra": [ 1, 113, 245, 81, 211, 201, 22, 238, 155, 88, 173, 43, 216, 198, 170, 9, 214, 147, 135, 107, 168, 254, 28, 231, 35, 92, 157, 134, 14, 147, 233, 74, 193, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: