Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469e7e5853e0d530a1cb727f1ec2cb319b567945fbd7d18bd8cc9b7f282e2783

Tx prefix hash: fda96722f4a01957e225ef7a15e8e21c58c64b38a873b67ec0ca87d6e1b9916d
Tx public key: 28d9d6541162ddd51d2d34ed8f4292f326340b3ee8874f010c44de2d3a95bcb7
Timestamp: 1785124651 Timestamp [UTC]: 2026-07-27 03:57:31 Age [y:d:h:m:s]: 00:118:07:14:38
Block: 1599225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 84269 RingCT/type: yes/0
Extra: 0128d9d6541162ddd51d2d34ed8f4292f326340b3ee8874f010c44de2d3a95bcb7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5e88ecb071dde77c84d94f2e89e61d39cee33930fedde5f1a5d1a7a4afe81501 0.000600000000 2089243 of 15 <41>

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": 1599235, "vin": [ { "gen": { "height": 1599225 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "5e88ecb071dde77c84d94f2e89e61d39cee33930fedde5f1a5d1a7a4afe81501", "view_tag": "41" } } } ], "extra": [ 1, 40, 217, 214, 84, 17, 98, 221, 213, 29, 45, 52, 237, 143, 66, 146, 243, 38, 52, 11, 62, 232, 135, 79, 1, 12, 68, 222, 45, 58, 149, 188, 183 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: