Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f905331391395826e8a0ac68fa7f90fdf10cbe8483eb6d4cee630ed1f736303

Tx prefix hash: 2b9482f8cf9c74b78be357134b400bdf962740160dc448c0455b499ad4c3d40a
Tx public key: 4d00764ec7f20323dd08fde7af6dcea520e588a597ee9988e9c2d22efae0341d
Timestamp: 1705992045 Timestamp [UTC]: 2024-01-23 06:40:45 Age [y:d:h:m:s]: 02:300:21:59:38
Block: 941384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740254 RingCT/type: yes/0
Extra: 014d00764ec7f20323dd08fde7af6dcea520e588a597ee9988e9c2d22efae0341d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6efbfc1539824b2cce237bbab8b89c73be7a902f57d0e88d5de1d424044fee6d 0.000600000000 1399530 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": 941394, "vin": [ { "gen": { "height": 941384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6efbfc1539824b2cce237bbab8b89c73be7a902f57d0e88d5de1d424044fee6d" } } ], "extra": [ 1, 77, 0, 118, 78, 199, 242, 3, 35, 221, 8, 253, 231, 175, 109, 206, 165, 32, 229, 136, 165, 151, 238, 153, 136, 233, 194, 210, 46, 250, 224, 52, 29, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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: